btcwallet: Evaluate the properness of GetTransaction API confirmations patch
#10364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objectives
The goal of this PR is to make sure there are no unintended consequences of applying that btcwallet patch. This can be explicitly verified by making sure there are no relevant tests failing in the CI.
Motivation and Context
Follow-up on @yyforyongyu's comment btcsuite/btcwallet#1114 (review).
Triggering Points
This is the only place in LND codebase where
Confirmationsfield fromGetTransactionAPI is conditionally utilized:lnd/lnwallet/btcwallet/btcwallet.go
Lines 1292 to 1329 in af6816b
Pull Request Checklist
Testing
Code Style and Documentation
[skip ci]in the commit message for small changes.📝 Please see our Contribution Guidelines for further guidance.